System and method for secure file-sharing via a distributed network

ABSTRACT

Systems, computer program products, and methods are described herein for secure file-sharing. The present invention may be configured to receive a request to store data on a network, process the request through a firewall. Processing the request includes: generating a first electronic digital certificate, storing the first electronic digital certificate on a distributed ledger, encrypting the data using the first electronic digital certificate, storing the encrypted data on at least one of the plurality of data server nodes, and recording the request on the distributed ledger. The present invention is further configured to receive and process a second request. Processing the second request includes: decrypting the data using the second electronic digital certificate, providing the decrypted data to the second requestor, and recording the second request on the distributed ledger.

FIELD OF THE INVENTION

The present invention embraces an electronic system for securefile-sharing.

BACKGROUND

The world is rapidly moving towards file-sharing storage such as clouddata storage for cost effective solutions. File-sharing methods such asthese involve saving important files, information, and data in a remotedatabase. These methods come with a particular set of vulnerabilitiesand security hazards. As these platforms are physically located with athird-party, the user may never be completely confident about datasecurity. Current methods of data security involve the installation offirewalls and the protection of data through authentication, howevervirtual and physical data misappropriation is still a possibility.Therefore, a need exists for a system and method to fully secure datafrom virtual and physical misappropriation.

SUMMARY

The following presents a simplified summary of one or more embodimentsof the present invention, in order to provide a basic understanding ofsuch embodiments. This summary is not an extensive overview of allcontemplated embodiments and is intended to neither identify key orcritical elements of all embodiments nor delineate the scope of any orall embodiments. This summary presents some concepts of one or moreembodiments of the present invention in a simplified form as a preludeto the more detailed description that is presented later.

In one aspect, a system for secure file-sharing is presented. The systemmay include at least one non-transitory storage device and at least oneprocessing device coupled to the at least one non-transitory storagedevice, where the at least one processing device may be configured to:receive a request, from a requestor, to store data on a network. Thenetwork may contain a plurality of data server nodes. The at least oneprocessing device may be further configured to process the requestthrough a firewall containing at least one edge node. Processing therequest may include the at least one edge node generating a firstelectronic digital certificate, storing the first electronic digitalcertificate on a distributed ledger, encrypting the data using the firstelectronic digital certificate, storing the encrypted data on at leastone of the plurality of data server nodes, and recording the request onthe distributed ledger.

The at least one processing device may be further configured to receivea second request, from a second requestor, to retrieve data from thenetwork. The second request may contain a second electronic digitalcertificate. The at least one processing device may be furtherconfigured to process the second request through a firewall containingat least one edge node. Processing the request may include the at leastone edge node retrieving the encrypted data from the at least one of theplurality of data server nodes, decrypting the data using the secondelectronic digital certificate, providing the decrypted data to thesecond requestor, and recording the second request on the distributedledger.

In another aspect, a computer program product for secure file-sharing ispresented. The computer program product may include a non-transitorycomputer-readable medium including code causing a first apparatus to:receive a request, from a requestor, to store data on a network. Thenetwork may contain a plurality of data server nodes. The non-transitorycomputer-readable medium may further include code causing a firstapparatus to process the request through a firewall containing at leastone edge node. Processing the request may include the at least one edgenode generating a first electronic digital certificate, storing thefirst electronic digital certificate on a distributed ledger, encryptingthe data using the first electronic digital certificate, storing theencrypted data on at least one of the plurality of data server nodes,and recording the request on the distributed ledger.

The non-transitory computer-readable medium may further include codecausing a first apparatus to receive a second request, from a secondrequestor, to retrieve data from the network. The second request maycontain a second electronic digital certificate. The non-transitorycomputer-readable medium may further include code causing a firstapparatus to process the second request through a firewall containing atleast one edge node. Processing the request may include retrieving theencrypted data from the at least one of the plurality of data servernodes, decrypting the data using the second electronic digitalcertificate, providing the decrypted data to the second requestor, andrecording the second request on the distributed ledger.

In yet another aspect, a method for secure file-sharing is provided. Themethod may include receiving a request, from a requestor, to store dataon a network. The network may contain a plurality of data server nodes.The method may further include processing the request through a firewallcontaining at least one edge node. Processing the request may includethe at least one edge node generating a first electronic digitalcertificate, storing the first electronic digital certificate on adistributed ledger, encrypting the data using the first electronicdigital certificate, storing the encrypted data on at least one of theplurality of data server nodes, and recording the request on thedistributed ledger.

The method may further include receiving a second request, from a secondrequestor, to retrieve data from the network. The second request maycontain a second electronic digital certificate. The method may furtherinclude processing the second request through a firewall containing atleast one edge node. Processing the request may include retrieving theencrypted data from the at least one of the plurality of data servernodes, decrypting the data using the second electronic digitalcertificate, providing the decrypted data to the second requestor, andrecording the second request on the distributed ledger.

In some embodiments, the at least one processing device is furtherconfigured to store the encrypted data on a secondary server.Additionally, or alternatively, the firewall further includes additionalauthentication requirements. In some embodiments, the network is aprivate network, a public network, or a hybrid network. Additionally, oralternatively, recording the request on the distributed ledger includesrecording information identifying at least one of an identification ofthe requestor, a geographical location of the requestor, or a time ofthe request. In some embodiments, the first electronic digitalcertificate and the second electronic digital certificate are the same.In other embodiments, the first electronic digital certificate and thesecond electronic digital certificate are different.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made the accompanying drawings, wherein:

FIG. 1 illustrates technical components of a system for securefile-sharing, in accordance with an embodiment of the invention;

FIG. 2 illustrates a process flow for secure file-sharing, in accordancewith an embodiment of the invention; and

FIG. 3 illustrates a network diagram for secure file-sharing, inaccordance with an embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Where possible, any terms expressed in the singularform herein are meant to also include the plural form and vice versa,unless explicitly stated otherwise. Also, as used herein, the term “a”and/or “an” shall mean “one or more,” even though the phrase “one ormore” is also used herein. Furthermore, when it is said herein thatsomething is “based on” something else, it may be based on one or moreother things as well. In other words, unless expressly indicatedotherwise, as used herein “based on” means “based at least in part on”or “based at least partially on.” Like numbers refer to like elementsthroughout.

As noted, to create a more secure file-sharing or cloud service, thesystem and method will utilize electronic digital certificates, such asnon-fungible tokens (NFTs). The electronic digital certificates willsecure the file-sharing platform by securing each server instance with adifferent and unique electronic digital certificate. The owner of thefile-sharing platform, their credentials, geographical location, cloudinstance credentials, and other information will form a unique alphanumeric pattern which will serve as the electronic digital certificate.The electronic digital certificate will be immutable and will be storedwith the file-sharing service organization. All electronic digitalcertificates will be stored in a distributed ledger, as well as anyactivity done on each node.

This technology will enable the file-sharing service to send the data tonearby edge nodes, the node may encrypt the data using the electronicdigital certificate and send the data back to the file-sharing service.Actual data will not be stored on the file-sharing platform. This willprevent physical data misappropriation as well. The data and filesstored on the file-sharing platform may also be protected via use of theelectronic digital certificate token as a password.

As used herein, an “entity” may be any institution employing informationtechnology resources and particularly technology infrastructureconfigured for processing large amounts of data. Typically, the data maybe related to products, services, and/or the like offered and/orprovided by the entity, customers of the entity, other aspect of theoperations of the entity, people who work for the entity, and/or thelike. As such, the entity may be an institution, group, association,financial institution, establishment, company, union, authority,merchant, service provider, and/or the like employing informationtechnology resources for processing large amounts of data. In someembodiments, the entity may be an institution, group, association,financial institution, establishment, company, union, authority,merchant, service provider, and/or the like hosting, sponsoring,coordinating, creating, and/or the like events, recognitions,achievements, and/or the like.

As used herein, a “user” may be an individual associated with an entity.As such, in some embodiments, the user may be an individual having pastrelationships, current relationships or potential future relationshipswith an entity. In some embodiments, a “user” may be an employee (e.g.,an associate, a project manager, a manager, an administrator, aninternal operations analyst, and/or the like) of the entity and/orenterprises affiliated with the entity, capable of operating systemsdescribed herein. In some embodiments, a “user” may be any individual,another entity, and/or a system who has a relationship with the entity,such as a customer, a prospective customer, and/or the like. In someembodiments, a user may be a system performing one or more tasksdescribed herein. In some embodiments, a user may be a verifiedauthority as described herein.

As used herein, a “user interface” may be any device or software thatallows a user to input information, such as commands and/or data, into adevice, and/or that allows the device to output information to the user.For example, a user interface may include an application programmerinterface (API), a graphical user interface (GUI), and/or an interfaceto input computer-executable instructions that direct a processingdevice to carry out functions. The user interface may employ inputand/or output devices to input data received from a user and/or outputdata to a user. Input devices and/or output devices may include adisplay, API, mouse, keyboard, button, touchpad, touch screen,microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/orother devices for communicating with one or more users.

As used herein, a “resource” may generally refer to objects, products,devices, goods, commodities, services, offers, discounts, currency,cash, cash equivalents, rewards, reward points, benefit rewards, bonusmiles, cash back, credits, and/or the like, and/or the ability andopportunity to access and use the same. Some example implementationsherein contemplate property held by a user, including property that isstored and/or maintained by a third-party entity. In some exampleimplementations, a resource may be associated with one or more accountsor may be property that is not associated with a specific account.Examples of resources associated with accounts may be accounts that havecash or cash equivalents, commodities, and/or accounts that are fundedwith or contain property, such as safety deposit boxes containingjewelry, art or other valuables, a trust account that is funded withproperty, and/or the like.

As used herein, a “source retainer” may generally refer to an account, asystem, and/or the like associated with a user and/or a type ofresources, such as software, a checking account, a deposit account, asavings account, a credit account, a rewards account, a rewards pointsaccount, a benefit rewards account, a bonus miles account, a cash backaccount, and/or the like, which may be managed and/or maintained by anentity, such as a financial institution, an electronic resource transferinstitution (e.g., a credit card company, a debit card company, aprepaid card company, and/or the like), a credit union, and/or the like.

As used herein, a “distribution” and/or an “allocation” may refer to anytransaction, activities, and/or communication between one or moreentities, between a user and one or more entities, and/or the like. Aresource distribution and/or an allocation of resources may refer to anydistribution of resources such as, but not limited to, a payment,processing of funds, purchase of goods or services, a return of goods orservices, a payment transaction, a credit transaction, otherinteractions involving a user's resource or account, and/or the like. Inthe context of an entity such as a financial institution, a resourcedistribution and/or an allocation of resources may refer to one or moreof a sale of goods and/or services, initiating an automated tellermachine (ATM) or online financial session, an account balance inquiry, arewards transfer, an account money transfer or withdrawal, opening afinancial application on a user's computer or mobile device, a useraccessing their e-wallet, any other interaction involving the userand/or the user's device that invokes and/or is detectable by thefinancial institution, and/or the like. In some embodiments, the usermay authorize a resource distribution and/or an allocation of resourcesusing a resource distribution instrument (e.g., credit cards, debitcards, checks, digital wallets, currency, loyalty points, and/or thelike) and/or resource distribution credentials (e.g., account numbers,resource distribution instrument identifiers, and/or the like). Aresource distribution and/or an allocation of resources may include oneor more of the following: renting, selling, and/or leasing goods and/orservices (e.g., groceries, stamps, tickets, DVDs, vending machine items,and/or the like); making payments to creditors (e.g., paying monthlybills; paying federal, state, and/or local taxes; and/or the like);sending remittances; loading money onto stored value cards (SVCs) and/orprepaid cards; donating to charities; and/or the like. Unlessspecifically limited by the context, a “resource distribution,” an“allocation of resources,” a “resource transfer,” a “transaction,” a“transaction event,” and/or a “point of transaction event” may refer toany activity between a user, a merchant, an entity, and/or the like. Insome embodiments, a resource distribution and/or an allocation ofresources may refer to financial transactions involving direct orindirect movement of funds through traditional paper transactionprocessing systems (e.g., paper check processing) or through electronictransaction processing systems. In this regard, resource distributionsand/or allocations of resources may refer to the user initiating apurchase for a product, service, or the like from a merchant. Typicalfinancial resource distribution and/or financial allocations ofresources include point of sale (POS) transactions, automated tellermachine (ATM) transactions, person-to-person (P2P) transfers, internettransactions, online shopping, electronic funds transfers betweenaccounts, transactions with a financial institution teller, personalchecks, conducting purchases using loyalty/rewards points, and/or thelike. When describing that resource transfers or transactions areevaluated, such descriptions may mean that the transaction has alreadyoccurred, is in the process of occurring or being processed, or has yetto be processed/posted by one or more financial institutions.

As used herein, “resource distribution instrument” may refer to anelectronic payment vehicle, such as an electronic credit, debit card,and/or the like, associated with a source retainer (e.g., a checkingaccount, a deposit account, a savings account, a credit account, and/orthe like). In some embodiments, the resource distribution instrument maynot be a “card” and may instead be account identifying informationstored electronically in a user device, such as payment credentialsand/or tokens and/or aliases associated with a digital wallet, accountidentifiers stored by a mobile application, and/or the like.

In some embodiments, the term “module” with respect to an apparatus mayrefer to a hardware component of the apparatus, a software component ofthe apparatus, and/or a component of the apparatus that includes bothhardware and software. In some embodiments, the term “chip” may refer toan integrated circuit, a microprocessor, a system-on-a-chip, amicrocontroller, and/or the like that may either be integrated into theexternal apparatus, may be inserted and/or removed from the externalapparatus by a user, and/or the like.

As used herein, an “engine” may refer to core elements of a computerprogram, part of a computer program that serves as a foundation for alarger piece of software and drives the functionality of the software,and/or the like. An engine may be self-contained but may includeexternally controllable code that encapsulates powerful logic designedto perform or execute a specific type of function. In one aspect, anengine may be underlying source code that establishes file hierarchy,input and/or output methods, how a part of a computer program interactsand/or communicates with other software and/or hardware, and/or thelike. The components of an engine may vary based on the needs of thecomputer program as part of the larger piece of software. In someembodiments, an engine may be configured to retrieve resources createdin other computer programs, which may then be ported into the engine foruse during specific operational aspects of the engine. An engine may beconfigurable to be implemented within any general-purpose computingsystem. In doing so, the engine may be configured to execute source codeembedded therein to control specific features of the general-purposecomputing system to execute specific computing operations, therebytransforming the general-purpose system into a specific purposecomputing system.

As used herein, a “component” of an application may include a softwarepackage, a service, a resource, a module, and/or the like that includesa set of related functions and/or data. In some embodiments, a componentmay provide a source capability (e.g., a function, a business function,and/or the like) to an application including the component. In someembodiments, components of an application may communicate with eachother via interfaces and may provide information to each otherindicative of the services and/or functions that other components mayutilize and/or how other components may utilize the services and/orfunctions. Additionally, or alternatively, components of an applicationmay be substitutable such that a component may replace anothercomponent. In some embodiments, components may include objects,collections of objects, and/or the like.

As used herein, “authentication credentials” may be any information thatmay be used to identify a user. For example, a system may prompt a userto enter authentication information such as a username, a password, atoken, a personal identification number (PIN), a passcode, biometricinformation (e.g., voice authentication, a fingerprint, and/or a retinascan), an answer to a security question, a unique intrinsic useractivity, such as making a predefined motion with a user device, and/orthe like. The authentication information may be used to authenticate theidentity of the user (e.g., determine that the authenticationinformation is associated with an account) and/or determine that theuser has authority to access an account or system. In some embodiments,the system may be owned and/or operated by an entity. In suchembodiments, the entity may employ additional computer systems, such asauthentication servers, to validate and certify resources inputted by aplurality of users within the system. The system may further useauthentication servers to certify the identity of users of the system,such that other users may verify the identity of the certified users. Insome embodiments, the entity may certify the identity of the users.Furthermore, authentication information and/or permission may beassigned to and/or required from a user, application, computing node,computing cluster, and/or the like to access stored data within at leasta portion of the system.

As used herein, an “interaction” may refer to any communication betweenone or more users, one or more entities or institutions, and/or one ormore devices, nodes, clusters, and/or systems within the systemenvironment described herein. For example, an interaction may refer to atransfer of data between devices, an accessing of stored data by one ormore nodes of a computing cluster, a transmission of a requested task,and/or the like. In some embodiments, an interaction may refer to anentity, a user, a system, and/or a device providing an advertisement,information, data, a user interface, and/or the like to another entity,another user, another system, and/or another device.

As used herein, identifiers such as “first,” “second,” “third,” and/orthe like do not indicate a temporal relationship, unless explicitlystated. Such identifiers may modify instances of similar things and maybe used to differentiate between each of the instances.

As used herein, a “subset” may refer to one or more from a group. Forexample, a subset of users from a group of users may be one user fromthe group of users, multiple users from the group of users, or all ofthe users from the group of users. As another example, a subset ofproperties may be one property from the properties, multiple propertiesfrom the properties, or all of the properties.

FIG. 1 presents an exemplary block diagram of a system environment 100for secure file-sharing, in accordance with an embodiment of theinvention. FIG. 1 provides a system environment 100 that includesspecialized servers and a system communicably linked across adistributive network of nodes required to perform functions of processflows described herein in accordance with embodiments of the presentinvention.

As illustrated, the system environment 100 includes a network 110, asystem 130, and a user input system 140. Also shown in FIG. 1 is a userof the user input system 140. The user input system 140 may be a mobiledevice, a non-mobile computing device, and/or the like. The user may bea person who uses the user input system 140 to access, view modify,interact with, and/or the like information, data, images, video, and/orthe like. The user may be a person who uses the user input system 140 toinitiate, perform, monitor, and/or the like changes and/or modificationsto one or more systems, applications, services, and/or the like. The oneor more systems, applications, services, and/or the like may beconfigured to communicate with the system 130, input information onto auser interface presented on the user input system 140, and/or the like.The applications stored on the user input system 140 and the system 130may incorporate one or more parts of any process flow described herein.

As shown in FIG. 1 , the system 130 and the user input system 140 areeach operatively and selectively connected to the network 110, which mayinclude one or more separate networks. In some embodiments, the network110 may include a telecommunication network, local area network (LAN), awide area network (WAN), and/or a global area network (GAN), such as theInternet. Additionally, or alternatively, the network 110 may be secureand/or unsecure and may also include wireless and/or wired and/oroptical interconnection technology.

In some embodiments, the system 130 and the user input system 140 may beused to implement processes described herein, including user-side andserver-side processes including generating electronic digitalcertificates, encrypting data, decrypting data, and storing informationon a distributed ledger, in accordance with an embodiment of the presentinvention. The system 130 may represent various forms of digitalcomputers, such as laptops, desktops, workstations, personal digitalassistants, servers, blade servers, mainframes, and/or the like. Theuser input system 140 may represent various forms of mobile devices,such as personal digital assistants, cellular telephones, smartphones,smart glasses, and/or the like. The components shown here, theirconnections, their relationships, and/or their functions, are meant tobe exemplary only, and are not meant to limit implementations of theinventions described and/or claimed in this document.

In some embodiments, the system 130 may include a processor 102, memory104, a storage device 106, a high-speed interface 108 connecting tomemory 104, high-speed expansion ports 111, and a low-speed interface112 connecting to low-speed bus 114 and storage device 106. Each of thecomponents 102, 104, 106, 108, 111, and 112 may be interconnected usingvarious buses, and may be mounted on a common motherboard or in othermanners as appropriate. The processor 102 may process instructions forexecution within the system 130, including instructions stored in thememory 104 and/or on the storage device 106 to display graphicalinformation for a GUI on an external input/output device, such as adisplay 116 coupled to a high-speed interface 108. In some embodiments,multiple processors, multiple buses, multiple memories, multiple typesof memory, and/or the like may be used. Also, multiple systems, same orsimilar to system 130 may be connected, with each system providingportions of the necessary operations (e.g., as a server bank, a group ofblade servers, a multi-processor system, and/or the like). In someembodiments, the system 130 may be managed by an entity, such as abusiness, a merchant, a financial institution, a card managementinstitution, a software and/or hardware development company, a softwareand/or hardware testing company, and/or the like. The system 130 may belocated at a facility associated with the entity and/or remotely fromthe facility associated with the entity.

The memory 104 may store information within the system 130. In oneimplementation, the memory 104 may be a volatile memory unit or units,such as volatile random-access memory (RAM) having a cache area for thetemporary storage of information. In another implementation, the memory104 may be a non-volatile memory unit or units. The memory 104 may alsobe another form of computer-readable medium, such as a magnetic oroptical disk, which may be embedded and/or may be removable. Thenon-volatile memory may additionally or alternatively include an EEPROM,flash memory, and/or the like. The memory 104 may store any one or moreof pieces of information and data used by the system in which it residesto implement the functions of that system. In this regard, the systemmay dynamically utilize the volatile memory over the non-volatile memoryby storing multiple pieces of information in the volatile memory,thereby reducing the load on the system and increasing the processingspeed.

The storage device 106 may be capable of providing mass storage for thesystem 130. In one aspect, the storage device 106 may be or contain acomputer-readable medium, such as a floppy disk device, a hard diskdevice, an optical disk device, a tape device, a flash memory and/orother similar solid state memory device, and/or an array of devices,including devices in a storage area network or other configurations. Acomputer program product may be tangibly embodied in an informationcarrier. The computer program product may also contain instructionsthat, when executed, perform one or more methods, such as thosedescribed herein. The information carrier may be a non-transitorycomputer-readable or machine-readable storage medium, such as the memory104, the storage device 106, and/or memory on processor 102.

In some embodiments, the system 130 may be configured to access, via thenetwork 110, a number of other computing devices (not shown). In thisregard, the system 130 may be configured to access one or more storagedevices and/or one or more memory devices associated with each of theother computing devices. In this way, the system 130 may implementdynamic allocation and de-allocation of local memory resources amongmultiple computing devices in a parallel and/or distributed system.Given a group of computing devices and a collection of interconnectedlocal memory devices, the fragmentation of memory resources is renderedirrelevant by configuring the system 130 to dynamically allocate memorybased on availability of memory either locally, or in any of the othercomputing devices accessible via the network. In effect, the memory mayappear to be allocated from a central pool of memory, even though thememory space may be distributed throughout the system. Such a method ofdynamically allocating memory provides increased flexibility when thedata size changes during the lifetime of an application and allowsmemory reuse for better utilization of the memory resources when thedata sizes are large.

The high-speed interface 108 may manage bandwidth-intensive operationsfor the system 130, while the low-speed interface 112 and/or controllermanages lower bandwidth-intensive operations. Such allocation offunctions is exemplary only. In some embodiments, the high-speedinterface 108 is coupled to memory 104, display 116 (e.g., through agraphics processor or accelerator), and to high-speed expansion ports111, which may accept various expansion cards (not shown). In someembodiments, low-speed interface 112 and/or controller is coupled tostorage device 106 and low-speed bus 114 (e.g., expansion port). Thelow-speed bus 114, which may include various communication ports (e.g.,USB, Bluetooth, Ethernet, wireless Ethernet), may be coupled to one ormore input/output devices, such as a keyboard, a pointing device, ascanner, and/or a networking device such as a switch or router (e.g.,through a network adapter).

The system 130 may be implemented in a number of different forms, asshown in FIG. 1 . For example, it may be implemented as a standardserver or multiple times in a group of such servers. Additionally, oralternatively, the system 130 may be implemented as part of a rackserver system, a personal computer, such as a laptop computer, and/orthe like. Alternatively, components from system 130 may be combined withone or more other same or similar systems and the user input system 140may be made up of multiple computing devices communicating with eachother.

FIG. 1 also illustrates a user input system 140, in accordance with anembodiment of the invention. The user input system 140 may include aprocessor 152, memory 154, an input/output device such as a display 156,a communication interface 158, and a transceiver 160, among othercomponents, such as one or more image sensors. The user input system 140may also be provided with a storage device, such as a microdrive and/orthe like, to provide additional storage. Each of the components 152,154, 158, and 160, may be interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 152 may be configured to execute instructions within theuser input system 140, including instructions stored in the memory 154.The processor 152 may be implemented as a chipset of chips that includeseparate and multiple analog and/or digital processors. The processor152 may be configured to provide, for example, for coordination of theother components of the user input system 140, such as control of userinterfaces, applications run by user input system 140, and/or wirelesscommunication by user input system 140.

The processor 152 may be configured to communicate with the user throughcontrol interface 164 and display interface 166 coupled to a display156. The display 156 may be, for example, a Thin-Film-Transistor LiquidCrystal Display (TFT LCD) or an Organic Light Emitting Diode (OLED)display, and/or other appropriate display technology. An interface ofthe display 156 may include appropriate circuitry and may be configuredfor driving the display 156 to present graphical and other informationto a user. The control interface 164 may receive commands from a userand convert them for submission to the processor 152. In addition, anexternal interface 168 may be provided in communication with processor152 to enable near area communication of user input system 140 withother devices. External interface 168 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 154 may store information within the user input system 140.The memory 154 may be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory may also be provided andconnected to user input system 140 through an expansion interface (notshown), which may include, for example, a Single In Line Memory Module(SIMM) card interface. Such expansion memory may provide extra storagespace for user input system 140 and/or may store applications and/orother information therein. In some embodiments, expansion memory mayinclude instructions to carry out or supplement the processes describedabove and/or may include secure information. For example, expansionmemory may be provided as a security module for user input system 140and may be programmed with instructions that permit secure use of userinput system 140. Additionally, or alternatively, secure applicationsmay be provided via the SIMM cards, along with additional information,such as placing identifying information on the SIMM card in a securemanner. In some embodiments, the user may use applications to executeprocesses described with respect to the process flows described herein.For example, one or more applications may execute the process flowsdescribed herein. In some embodiments, one or more applications storedin the system 130 and/or the user input system 140 may interact with oneanother and may be configured to implement any one or more portions ofthe various user interfaces and/or process flow described herein.

The memory 154 may include, for example, flash memory and/or NVRAMmemory. In some embodiments, a computer program product may be tangiblyembodied in an information carrier. The computer program product maycontain instructions that, when executed, perform one or more methods,such as those described herein. The information carrier may be acomputer-readable or machine-readable medium, such as the memory 154,expansion memory, memory on processor 152, and/or a propagated signalthat may be received, for example, over transceiver 160 and/or externalinterface 168.

In some embodiments, the user may use the user input system 140 totransmit and/or receive information and/or commands to and/or from thesystem 130. In this regard, the system 130 may be configured toestablish a communication link with the user input system 140, wherebythe communication link establishes a data channel (wired and/orwireless) to facilitate the transfer of data between the user inputsystem 140 and the system 130. In doing so, the system 130 may beconfigured to access one or more aspects of the user input system 140,such as, a GPS device, an image capturing component (e.g., camera), amicrophone, a speaker, and/or the like.

The user input system 140 may communicate with the system 130 (and oneor more other devices) wirelessly through communication interface 158,which may include digital signal processing circuitry. Communicationinterface 158 may provide for communications under various modes orprotocols, such as GSM voice calls, SMS, EMS, or MMS messaging, CDMA,TDMA, PDC, WCDMA, CDMA2000, GPRS, and/or the like. Such communicationmay occur, for example, through transceiver 160. Additionally, oralternatively, short-range communication may occur, such as using aBluetooth, Wi-Fi, and/or other such transceiver (not shown).Additionally, or alternatively, a Global Positioning System (GPS)receiver module 170 may provide additional navigation-related and/orlocation-related wireless data to user input system 140, which may beused as appropriate by applications running thereon, and in someembodiments, one or more applications operating on the system 130.

The user input system 140 may also communicate audibly using audio codec162, which may receive spoken information from a user and convert it tousable digital information. Audio codec 162 may likewise generateaudible sound for a user, such as through a speaker (e.g., in a handset)of user input system 140. Such sound may include sound from voicetelephone calls, may include recorded sound (e.g., voice messages, musicfiles, and/or the like) and may also include sound generated by one ormore applications operating on the user input system 140, and in someembodiments, one or more applications operating on the system 130.

Various implementations of the systems and techniques described here maybe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof. Suchvarious implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and/or at least one output device.

Computer programs (e.g., also referred to as programs, software,applications, code, and/or the like) may include machine instructionsfor a programmable processor, and may be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” and/or “computer-readable medium” may refer to any computerprogram product, apparatus and/or device (e.g., magnetic discs, opticaldisks, memory, Programmable Logic Devices (PLDs), and/or the like) usedto provide machine instructions and/or data to a programmable processor,including a machine-readable medium that receives machine instructionsas a machine-readable signal. The term “machine-readable signal” mayrefer to any signal used to provide machine instructions and/or data toa programmable processor.

To provide for interaction with a user, the systems and/or techniquesdescribed herein may be implemented on a computer having a displaydevice (e.g., a CRT (cathode ray tube), an LCD (liquid crystal display)monitor, and/or the like) for displaying information to the user, akeyboard by which the user may provide input to the computer, and/or apointing device (e.g., a mouse or a trackball) by which the user mayprovide input to the computer. Other kinds of devices may be used toprovide for interaction with a user as well. For example, feedbackprovided to the user may be any form of sensory feedback (e.g., visualfeedback, auditory feedback, and/or tactile feedback). Additionally, oralternatively, input from the user may be received in any form,including acoustic, speech, and/or tactile input.

The systems and techniques described herein may be implemented in acomputing system that includes a back end component (e.g., as a dataserver), that includes a middleware component (e.g., an applicationserver), that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usermay interact with an implementation of the systems and techniquesdescribed here), and/or any combination of such back end, middleware,and/or front end components. Components of the system may beinterconnected by any form or medium of digital data communication(e.g., a communication network). Examples of communication networksinclude a local area network (“LAN”), a wide area network (“WAN”),and/or the Internet.

In some embodiments, computing systems may include clients and servers.A client and server may generally be remote from each other andtypically interact through a communication network. The relationship ofclient and server may arise by virtue of computer programs running onthe respective computers and having a client-server relationship to eachother.

The embodiment of the system environment 100 illustrated in FIG. 1 isexemplary and other embodiments may vary. As another example, in someembodiments, the system 130 includes more, less, or differentcomponents. As another example, in some embodiments, some or all of theportions of the system environment 100, the system 130, and/or the userinput system 140 may be combined into a single portion. Likewise, insome embodiments, some or all of the portions of the system environment100, the system 130, and/or the user input system 140 may be separatedinto two or more distinct portions.

In some embodiments, the system environment may 100 include one or moreuser input systems, one or more electronic digital certificategenerating systems, and/or one or more server systems (e.g., similar tothe system 130 and/or the user input system 140) associated with anentity (e.g., a business, a merchant, a financial institution, a cardmanagement institution, an software and/or hardware development company,a software and/or hardware testing company, and/or the like). Forexample, a user (e.g., an employee, a customer, and/or the like) may usea user input system (e.g., similar to the user input system 140) tostore data and/or the like using one or more systems, applications,services, and/or the like (e.g., similar to the system 130, running asystem similar to the system 130, and/or the like) and the user inputsystem may encrypt the data using the electronic digital certificate anddistributed ledger (e.g., similar to the system 130, running a systemsimilar to the system 130, and/or the like). In some embodiments, theuser input system, the electronic digital certificate generating system,and/or the server system associated with the entity may perform one ormore of the steps described herein with respect to the process flowsdescribed herein with respect to FIG. 2 .

FIG. 2 illustrates a process flow 200 for secure file-sharing, inaccordance with an embodiment of the invention. In some embodiments, thesecure file-sharing system and/or the like (e.g. similar to one or moreof the systems described herein with respect to FIG. 1 ) may perform oneor more of the steps of process flow 200.

As shown in block 210, the process flow 200 may include receiving arequest to store data on a network from a first requestor. For example,a requestor, or user, may request to store data on a network or serversuch as a cloud network or cloud server. Additionally, or alternativelya requestor, or user, may request to retrieve data from the network orserver.

As shown in block 220, the process flow 200 may include processing therequest through a firewall. For example, processing the request througha firewall may include processing the request through a security system.The firewall, or security system, may be set up by the entity. Thefirewall may also be setup by the manager of the server. In someembodiments, there is more than one firewall. The firewall contains atleast one edge node. The edge node performs the functions required toprocess the request.

As shown in block 221, the process flow 200 may include, as part ofprocessing the request, generating a first electronic digitalcertificate. An electronic digital certificate is a unique unit of datastored on a distributed ledger. The electronic digital certificate maybe a non-fungible token (NFT).

As shown in block 222, the process flow 200 may include, as part ofprocessing the request, storing the first electronic digital certificateon a distributed ledger. The distributed ledger may be a publicdistributed ledger or a private distributed ledger.

As shown in block 223, the process flow 200 may include, as part ofprocessing the request, encrypting the data using the first electronicdigital certificate. The electronic digital certificate is used as a keyfor encrypting the data for storage.

As shown in block 224, the process flow 200 may include, as part ofprocessing the request, storing the encrypted data on a data servernode. The encrypted data is stored on at least one of the plurality ofdata server nodes.

As shown in block 225, the process flow 200 may include, as part ofprocessing the request, recording the request on the distributed ledger.The request is recorded to keep a record of the data. For example, who,when, and where the data was accessed may be recorded, as well as who,when, and where the data was created.

As shown in block 230, the process flow 200 may include receiving asecond request to retrieve data from the network. The second request maycome from a second requestor. The second requestor may be the same asthe first requestor, or the second requestor may be different from thefirst requestor.

As shown in block 240, the process flow 200 may include processing therequest through the firewall. In some embodiments, there is more thanone firewall. The firewall contains at least one edge node. The edgenode performs the functions required to process the request.

As shown in block 241, the process flow 200 may include, as part ofprocessing the request, retrieving the encrypted data from at least oneof the plurality of data server nodes.

As shown in block 242, the process flow 200 may include, as part ofprocessing the request, decrypting the data using the second electronicdigital certificate. The second electronic digital certificate serves asa key for decrypting the data.

As shown in block 243, the process flow 200 may include, as part ofprocessing the request, providing the decrypted data to the secondrequestor.

As shown in block 244, the process flow 200 may include, as part ofprocessing the request, recording the second request on the distributedledger.

In a first embodiment, the system may store the encrypted data on asecondary server. This may be done to back-up the data.

In a second embodiment alone or in combination with the firstembodiment, the firewall may have additional authenticationrequirements. Authentication requirements include but are not limited toa password or a one-time authentication event.

In a third embodiment alone or in combination with any of the firstthrough second embodiments, recording the request on the distributedledger includes recording information identifying at least one of anidentification of the requestor, a geographical location of therequestor, or a time of the request.

In a fourth embodiment alone or in combination with any of the firstthrough third embodiments, the first electronic digital certificate andthe second electronic digital certificate may be the same. This allowsfor symmetric cryptography, where the same electronic digitalcertificate is used to encrypt and decrypt the data.

In a fifth embodiment alone or in combination with any of the firstthrough fourth embodiments, the first electronic digital certificate andthe second electronic digital certificate may be different. This allowsfor asymmetric cryptography, where different electronic digitalcertificates are used to encrypt and decrypt the data.

Although FIG. 2 shows example blocks of process flow 200, in someembodiments, process flow 200 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 2 . Additionally, or alternatively, two or more of theblocks of process flow 200 may be performed in parallel.

As shown in FIG. 3 , the server or network 300 is comprised of multipleserver nodes 301, 302, 303, 304, and 305. The system stores theelectronic digital certificates 311, 312, 313, 314, and 315 on adistributed ledger 325. The data and the electronic digital certificates311, 312, 313, 314, and 315 are processed through the firewall 320,which contains at least one edge node, to encrypt the data using theelectronic digital certificates and to store the encrypted data on theserver nodes 301. 302, 303, 304, and 304 within the server or network300. The firewall 320 contains at least one edge node.

As will be appreciated by one of ordinary skill in the art in view ofthis disclosure, the present invention may include and/or be embodied asan apparatus (including, for example, a system, machine, device,computer program product, and/or the like), as a method (including, forexample, a business method, computer-implemented process, and/or thelike), or as any combination of the foregoing. Accordingly, embodimentsof the present invention may take the form of an entirely businessmethod embodiment, an entirely software embodiment (including firmware,resident software, micro-code, stored procedures in a database, or thelike), an entirely hardware embodiment, or an embodiment combiningbusiness method, software, and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product thatincludes a computer-readable storage medium having one or morecomputer-executable program code portions stored therein. As usedherein, a processor, which may include one or more processors, may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing one or more computer-executableprogram code portions embodied in a computer-readable medium, and/or byhaving one or more application-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, electromagnetic, infrared, and/orsemiconductor system, device, and/or other apparatus. For example, insome embodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as, forexample, a propagation signal including computer-executable program codeportions embodied therein.

One or more computer-executable program code portions for carrying outoperations of the present invention may include object-oriented,scripted, and/or unscripted programming languages, such as, for example,Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript,and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

Some embodiments of the present invention are described herein withreference to flowchart illustrations and/or block diagrams of apparatusand/or methods. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and/or combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions. These one or more computer-executable program code portionsmay be provided to a processor of a general purpose computer, specialpurpose computer, and/or some other programmable data processingapparatus in order to produce a particular machine, such that the one ormore computer-executable program code portions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, create mechanisms for implementing the steps and/or functionsrepresented by the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may be storedin a transitory and/or non-transitory computer-readable medium (e.g. amemory) that may direct, instruct, and/or cause a computer and/or otherprogrammable data processing apparatus to function in a particularmanner, such that the computer-executable program code portions storedin the computer-readable medium produce an article of manufactureincluding instruction mechanisms which implement the steps and/orfunctions specified in the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with, and/or replaced with,operator- and/or human-implemented steps in order to carry out anembodiment of the present invention.

Although many embodiments of the present invention have just beendescribed above, the present invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Also, it will beunderstood that, where possible, any of the advantages, features,functions, devices, and/or operational aspects of any of the embodimentsof the present invention described and/or contemplated herein may beincluded in any of the other embodiments of the present inventiondescribed and/or contemplated herein, and/or vice versa. In addition,where possible, any terms expressed in the singular form herein aremeant to also include the plural form and/or vice versa, unlessexplicitly stated otherwise. Accordingly, the terms “a” and/or “an”shall mean “one or more,” even though the phrase “one or more” is alsoused herein. Like numbers refer to like elements throughout.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments may be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

What is claimed is:
 1. A system for secure file-sharing, the systemcomprising at least one non-transitory storage device, and at least oneprocessing device coupled to the at least one non-transitory storagedevice, wherein the at least one processing device is configured to:receive a request, from a requestor, to store data on a network, whereinthe network comprises a plurality of data server nodes; process therequest through a firewall, wherein the firewall comprises at least oneedge node, wherein processing the request comprises: the at least oneedge node generating a first electronic digital certificate, the atleast one edge node storing the first electronic digital certificate ona distributed ledger, the at least one edge node encrypting the datausing the first electronic digital certificate, the at least one edgenode storing the encrypted data on at least one of the plurality of dataserver nodes, and the at least one edge node recording the request onthe distributed ledger; receive a second request, from a secondrequestor, to retrieve data from the network, wherein the requestcomprises a second electronic digital certificate; and process thesecond request through the firewall, wherein processing the secondrequest comprises: the at least one edge node retrieving the encrypteddata from the at least one of the plurality of data server nodes, the atleast one edge node decrypting the data using the second electronicdigital certificate, the at least one edge node providing the decrypteddata to the second requestor, and the at least one edge node recordingthe second request on the distributed ledger.
 2. The system for securefile-sharing according to claim 1, wherein the at least one processingdevice is further configured to store the encrypted data on a secondaryserver.
 3. The system for secure file-sharing according to claim 1,wherein the firewall further comprises additional authenticationrequirements.
 4. The system for secure file-sharing according to claim1, wherein the network is a private network, a public network, or ahybrid network.
 5. The system for secure file-sharing according to claim1, wherein recording the request on the distributed ledger comprisesrecording information identifying at least one of an identification ofthe requestor, a geographical location of the requestor, or a time ofthe request.
 6. The system for secure file-sharing according to claim 1,wherein the first electronic digital certificate and the secondelectronic digital certificate are the same.
 7. The system for securefile-sharing according to claim 1, wherein the first electronic digitalcertificate and the second electronic digital certificate are different.8. A computer program product for secure file-sharing, the computerprogram product comprising a non-transitory computer-readable mediumcomprising code causing a first apparatus to: receive a request, from arequestor, to store data on a network, wherein the network comprises aplurality of data server nodes; process the request through a firewall,wherein the firewall comprises at least one edge node, whereinprocessing the request comprises: the at least one edge node generatinga first electronic digital certificate, the at least one edge nodestoring the first electronic digital certificate on a distributedledger, the at least one edge node encrypting the data using the firstelectronic digital certificate, the at least one edge node storing theencrypted data on at least one of the plurality of data server nodes,and the at least one edge node recording the request on the distributedledger; receive a second request, from a second requestor, to retrievedata from the network, wherein the request comprises a second electronicdigital certificate; and process the second request through thefirewall, wherein processing the second request comprises: the at leastone edge node retrieving the encrypted data from the at least one of theplurality of data server nodes, the at least one edge node decryptingthe data using the second electronic digital certificate, the at leastone edge node providing the decrypted data to the second requestor, andthe at least one edge node recording the second request on thedistributed ledger.
 9. The computer program product for securefile-sharing according to claim 8, wherein the at least one processingdevice is further configured to store the encrypted data on a secondaryserver.
 10. The computer program product for secure file-sharingaccording to claim 8, wherein the firewall further comprises additionalauthentication requirements.
 11. The computer program product for securefile-sharing according to claim 8, wherein the network is a privatenetwork, a public network, or a hybrid network.
 12. The computer programproduct for secure file-sharing according to claim 8, wherein recordingthe request on the distributed ledger comprises recording informationidentifying at least one of an identification of the requestor, ageographical location of the requestor, or a time of the request. 13.The computer program product for secure file-sharing according to claim8, wherein the first electronic digital certificate and the secondelectronic digital certificate are the same.
 14. The computer programproduct for secure file-sharing according to claim 8, wherein the firstelectronic digital certificate and the second electronic digitalcertificate are different.
 15. A method for secure file-sharing, themethod comprising: receiving a request, from a requestor, to store dataon a network, wherein the network comprises a plurality of data servernodes; processing the request through a firewall, wherein the firewallcomprises at least one edge node, wherein processing the requestcomprises: the at least one edge node generating a first electronicdigital certificate, the at least one edge node storing the firstelectronic digital certificate on a distributed ledger, the at least oneedge node encrypting the data using the first electronic digitalcertificate, the at least one edge node storing the encrypted data on atleast one of the plurality of data server nodes, and the at least oneedge node recording the request on the distributed ledger; receiving asecond request, from a second requestor, to retrieve data from thenetwork, wherein the request comprises a second electronic digitalcertificate; and processing the second request through the firewall,wherein processing the second request comprises: the at least one edgenode retrieving the encrypted data from the at least one of theplurality of data server nodes, the at least one edge node decryptingthe data using the second electronic digital certificate, the at leastone edge node providing the decrypted data to the second requestor, andthe at least one edge node recording the second request on thedistributed ledger.
 16. The method for secure file-sharing according toclaim 15, wherein the at least one processing device is furtherconfigured to store the encrypted data on a secondary server.
 17. Themethod for secure file-sharing according to claim 15, wherein thefirewall further comprises additional authentication requirements. 18.The method for secure file-sharing according to claim 15, wherein thenetwork is a private network, a public network, or a hybrid network. 19.The method for secure file-sharing according to claim 15, whereinrecording the request on the distributed ledger comprises recordinginformation identifying at least one of an identification of therequestor, a geographical location of the requestor, or a time of therequest.
 20. The method for secure file-sharing according to claim 15,wherein the first electronic digital certificate and the secondelectronic digital certificate are the same.